Skip to content

docs(ledger): record the merge outcome for PR #2573 - #2576

Merged
BigSimmo merged 9 commits into
mainfrom
claude/prlanded-2573-ledger
Sep 3, 2026
Merged

docs(ledger): record the merge outcome for PR #2573#2576
BigSimmo merged 9 commits into
mainfrom
claude/prlanded-2573-ledger

Conversation

@BigSimmo

@BigSimmo BigSimmo commented Sep 2, 2026 •
edited by cursor Bot
Loading

Copy link
Copy Markdown
Owner

Summary

  • Add the immutable prlanded review record for PR docs: full repository audit 2026-09-02 (audit only, nothing acted on) #2573 (the 2026-09-02 full repository audit), written by npm run ledger:append — never by hand. It records that the PR squash-merged to main as dfa863e57, that the branch tip's content diff against the squash commit is empty (nothing orphaned by the auto-merge race), and the CI evidence on the merged head.
  • Regenerate data/repo-awareness-snapshot.json, which the new record forces (its review-record list gains one entry).

Two files. No code, migration, script, workflow, gate, test, ledger table or inbox request is changed. Nothing under src/, supabase/, worker/, scripts/ or .github/ is touched.

RAG impact: none — no RAG surface is touched.

Verification

  • npm run check:branch-review-ledger — Branch review ledger guard passed: 880 live table records + 1206 archived + 589 immutable …
  • npm run check:repo-awareness-snapshot — [repo-awareness] in step with data/repo-awareness-snapshot.json (197 pages, 587 documents, 2675 reviews)
  • npx prettier --check on both changed files — All matched files use Prettier code style!
  • npm run verify:pr-local — running locally at publication (the snapshot path routes this two-file PR to the heavy plan: lint, typecheck, full unit suite, build); the closing summary line is added to this body when it completes.

Verification not run: npm run verify:ui — no UI, routing, styling or browser behaviour changed.
Verification not run: npm run verify:release — no release or handoff confidence is claimed.
Verification not run: npm run check:production-readiness and every eval:* — provider-backed; nothing here changes clinical workflow, privacy, environment, Supabase, source governance or deployment behaviour.

No provider-backed gate was run and nothing touching OpenAI, Supabase, Railway, Sentry or live CI was executed.

Risk and rollout

  • Risk: low — one new review record and its generated snapshot.
  • Rollback: revert the single commit; the snapshot regenerates from the tree.
  • Provider or production effects: None.
  • RAG impact: none.

Clinical Governance Preflight

Classified clinical-risk only because data/repo-awareness-snapshot.json regenerates; that regeneration is the mechanical output of the committed generator. Each item is confirmed against the two-file diff.

  • Source-backed claims still require linked source verification before clinical use — no answer-path, source-rendering or citation code is touched.
  • No patient-identifiable document workflow was introduced or expanded without explicit governance approval — no workflow code is touched.
  • Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy) — no Supabase env value, migration or configured target changes.
  • Service-role keys and private document access remain server-only — no src/ change.
  • Demo/synthetic content remains clearly separated from real clinical sources — untouched.
  • Source metadata, review status, and outdated/unknown-source behavior remain conservative — untouched.
  • Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed — no clinical decision-support behaviour changed.

Notes

  • Delivered on a fresh branch rather than the audit branch because the repository's permission rules block force pushes, and the audit branch's remote history was already squash-merged.
  • Housekeeping only; merge whenever convenient.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FSPY4VSqg7WVukCvmHQP9t

Generated by Claude Code

Note

Low Risk
Documentation and generated repo-metadata only; no runtime, auth, or data-path changes.

Overview
Adds an immutable prlanded branch-review record for PR #2573 (2026-09-02 full repository audit), documenting the squash merge to dfa863e57, empty branch-tip vs squash diff, and green CI on the merged head.

Regenerates data/repo-awareness-snapshot.json so captured_revision points at that merge and the embedded review history picks up the new ledger row (plus other recent prlanded entries already on the branch timeline in the generator output).

Also adds a separate immutable record for PR #2576 drift repair (snapshot-only merge conflict resolved by re-running the snapshot generator). No application code, workflows, or clinical/RAG surfaces change.

Reviewed by Cursor Bugbot for commit dbaac82. Configure here.

@claude
docs(ledger): record the merge outcome for PR #2573
609bb83 
Immutable prlanded review record for the full repository audit: PR #2573
squash-merged to main as dfa863e; the branch tip's content diff against the
squash commit is empty, so nothing was orphaned. Regenerates the repo-awareness
snapshot the new record forces.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FSPY4VSqg7WVukCvmHQP9t
@coderabbitai

coderabbitai Bot commented Sep 2, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: 973aee96-d6ad-4ea6-a119-6ec07f5de4df

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@supabase

supabase Bot commented Sep 2, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@BigSimmo
BigSimmo marked this pull request as ready for review September 3, 2026 00:08
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 3, 2026 •
edited
Loading

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-03T00:13:49.100166Z 609bb83 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@cursor

cursor Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_09a81c59-6d42-4edd-8978-42f0be81946f)

@BigSimmo
BigSimmo enabled auto-merge (squash) September 3, 2026 18:21
@claude
Merge remote-tracking branch 'origin/main' into claude/prlanded-2573-…
b512367 
…ledger

# Conflicts:
#	data/repo-awareness-snapshot.json
@cursor

cursor Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_ea765cd3-4523-4983-820f-b09b613a72a5)

claude and others added 2 commits September 3, 2026 18:29
@claude
docs(ledger): record Run PR sweep drift repair for PR #2576
1193987 
Merged origin/main into claude/prlanded-2573-ledger to resolve a real
conflict confined to data/repo-awareness-snapshot.json, regenerated
via its committed generator, and pushed. No review threads were open.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0137etKe6X2p9HkXsXoYY8TA
@BigSimmo
Merge branch 'main' into claude/prlanded-2573-ledger
7738784
@BigSimmo
BigSimmo disabled auto-merge September 3, 2026 18:35
@BigSimmo
BigSimmo enabled auto-merge (squash) September 3, 2026 19:24
@cursor

cursor Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_3c069326-af3a-4e3e-912e-300e42f7e5ee)

@BigSimmo
BigSimmo merged commit c3f8b46 into main Sep 3, 2026
33 checks passed
@BigSimmo
BigSimmo deleted the claude/prlanded-2573-ledger branch September 3, 2026 19:54
BigSimmo pushed a commit that referenced this pull request Sep 4, 2026
@claude
docs(audit): record that P1 (#2580) and the ledger record (#2576) merged
3343f15 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FSPY4VSqg7WVukCvmHQP9t
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@BigSimmo @claude